Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix readyz endpoint not returning correct status when using database dynamic registration #11160

Merged
merged 5 commits into from
Mar 25, 2022

Conversation

gabrielcorado
Copy link
Contributor

Closes #10077.

Change the database service start to always send a heartbeat initial when no static databases are configured. This doesn't change the current behavior where the agent doesn't wait for the dynamic databases to be discovered. It was tested with the "Reproduction steps" described in the issue.

Note: The application server also has this issue. The idea is to do the same fix after it is approved.

@gabrielcorado gabrielcorado self-assigned this Mar 15, 2022
@github-actions github-actions bot added the database-access Database access related issues and PRs label Mar 15, 2022
Copy link
Collaborator

@r0mant r0mant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3-line fix and 150 lines of tests. Nice!

@nklaassen nklaassen removed their request for review March 23, 2022 20:23
@gabrielcorado gabrielcorado enabled auto-merge (squash) March 25, 2022 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database-access Database access related issues and PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

readyz endpoint returns incorrect status on DB agent when using dynamic registration
5 participants